react-native-screens 4.24+ requires RN 0.77+ codegen.

Co-Authored-By: Claude Opus 4.6 <[email protected]>

Align with purchaseTesterTypescript patterns: ignore .yarn cache,
.xcode.env.local, Xcode artifacts, and stop over-ignoring xcworkspace.

Co-Authored-By: Claude Opus 4.6 <[email protected]>

Replace Objective-C AppDelegate (AppDelegate.h, AppDelegate.mm, main.m)
with a Swift AppDelegate using @main annotation. Also adds required
devDependencies for pod install to work correctly.

Co-Authored-By: Claude Opus 4.6 <[email protected]>

Co-Authored-By: Claude Opus 4.6 <[email protected]>
Made-with: Cursor

The StoreKitConfiguration.storekit file was on disk but not registered
as a PBXFileReference in project.pbxproj, so Xcode couldn't find it
at runtime. Also fix the scheme identifier path.

Made-with: Cursor

The identifier is relative to the .xcodeproj directory, so it needs
the ../ prefix to reach the sibling StoreKitConfiguration.storekit.

Made-with: Cursor

Made-with: Cursor

Made-with: Cursor

Made-with: Cursor

Made-with: Cursor

Made-with: Cursor

… add testID

- Add e2e-tests/MaestroTestApp to root workspaces (matching
  purchaseTesterTypescript pattern)
- Replace portal: deps with babel module-resolver aliases to SDK source
- Configure Metro watchFolders + exclusionList for out-of-root resolution
- Surface presentPaywall errors in a visible <Text testID="error-message">
  instead of only console.error, so Maestro can capture failures
- Switch from accessibilityLabel to testID for reliable Maestro targeting
- Update README to describe the workspace + module-resolver mechanism

Made-with: Cursor

…ile.lock

- Add .catch() to getCustomerInfo() to surface errors in the UI instead
  of producing an unhandled promise rejection
- Replace deprecated blacklistRE with blockList in metro.config.js
- Regenerate Podfile.lock under current workspace setup (was generated
  under the old portal: setup)

Made-with: Cursor

Made-with: Cursor

Include react-native-purchases and react-native-purchases-ui as Gradle
projects so the Android autolinker can resolve them. Mirrors the
purchaseTesterTypescript example.

Made-with: Cursor

RN 0.76.x is incompatible with react-native-purchases-ui's AGP 8.13.2
(NativeDeviceEventManagerSpec unresolved supertype during Kotlin compilation).

- React Native 0.76.9 → 0.78.0 (+ React 19, safe-area-context 5, screens 4.5)
- Gradle wrapper 8.10.2 → 8.14.4
- Kotlin 1.9.25 → 2.0.21, NDK 26 → 27, targetSdk 34 → 35
- Add allprojects repositories block and explicit Gradle project includes
- Regenerate Podfile.lock and yarn.lock

Made-with: Cursor

react-native-screens 4.24.0 has a codegen incompatibility with
RN 0.78 ("Unknown prop type for accessibilityContainerViewIsModal").
Pin to ~4.11.0 (matching purchaseTesterTypescript) and regenerate
both yarn.lock and Podfile.lock.

Made-with: Cursor

Made-with: Cursor

The CLI is a devDependency of react-native (not production), so it's
not installed transitively. Both pod install (use_native_modules!) and
Gradle autolinking (RNGP) require it to discover native modules.

Made-with: Cursor

Resolve yarn.lock conflict by regenerating.

Made-with: Cursor

- Replace force-unwrap in bundleURL() with guard + fatalError for a
  more debuggable crash when main.jsbundle is missing
- Add comment in babel.config.js explaining how SDK packages are
  resolved from repo source without being in package.json dependencies

Made-with: Cursor

The committed Podfile.lock goes stale when yarn resolves a different
react-native patch (hermes-engine version changes). Since this is a
CI-only test app rebuilt from scratch every run, not committing the
lockfile avoids the staleness problem.

Made-with: Cursor

Reverting the previous decision to gitignore Podfile.lock. Instead,
we'll enforce immutable yarn installs on CI (no YARN_ENABLE_IMMUTABLE_INSTALLS=false)
so versions don't drift, and the committed Podfile.lock stays consistent
with yarn.lock.

Made-with: Cursor

MaestroTestApp is a workspace of the root package.json, so the root
yarn.lock is the source of truth. The local yarn.lock was an artifact
from project initialization and was pinning [email protected] while
the root lockfile pins 0.78.0, causing immutable install failures on CI.

Made-with: Cursor

react-native 0.78.0 ships a fmt version with consteval C++20 errors
when compiled with Xcode 26.4's clang. Pinning to 0.78.3 which
includes the fix. Updated yarn.lock and Podfile.lock accordingly.

Made-with: Cursor

react-native 0.78.0 ships an fmt version with consteval C++20
compilation errors on Xcode 26.4's clang. Bumping all workspaces to
0.78.3 (patch update) which includes the fix. This also keeps a single
react-native version across workspaces, ensuring proper Yarn hoisting
of shared dependencies like @react-native/babel-preset.

Reverts the MaestroTestApp exact pin to ^0.78.0 (range) since the
lockfile now resolves all ^0.78.0 ranges to 0.78.3.

Made-with: Cursor

Reverting the attempt to commit Podfile.lock and bump react-native
to 0.78.3. The react-native version update is out of scope for the
Maestro e2e test setup.

Instead, Podfile.lock remains gitignored and will be generated fresh
on each CI run using YARN_ENABLE_IMMUTABLE_INSTALLS=false (in PR3)
to let yarn resolve the latest compatible react-native patch.

Made-with: Cursor